Use packer plugins install --path to install (development version) #131
Conversation
|
Need to tweak this a bit, hold on :) |
|
Should we just update the |
|
That would also work yepp :) It doesn't have an install rule though, which would be nice to have, and the install rule shouldn't do One other thing I had to do was to update our version in |
|
One missing piece here is that Packer doesn't easily allow you to run a Packer template with |
With modern Packer, and Packer templates with required_plugins sections, the plugins need to follow a specific folder structure and also come with a sha256 hash of the plugin. By using `packer plugins install --path` we can let Packer deal with the specifics of installing a plugin from disk instead of from a repository. As a drive-by, update the version number in version.go to match the latest tagged version. This version number should always reflect the current version.
|
Like this? |
|
We could adopt the entire |
Looks like Packer just got the missing bits to support this use case :) See hashicorp/packer#12749 (comment) |
With modern Packer, and Packer templates with required_plugins sections, the plugins need to follow a specific folder structure and also come with a sha256 hash of the plugin.
By using
packer plugins install --pathwe can let Packer deal with the specifics of installing a plugin from disk instead of from a repository.